<?php
// settings.php

/**
 * DSF site-specific configuration file.
 *
 * IMPORTANT NOTE:
 * This file may have been set to read-only by the DSF installation
 * program. If you make changes to this file, be sure to protect it again
 * after making your modifications. Failure to remove write permissions
 * to this file is a security risk.
 */

/**
 * Database settings:
 *
 * The $databases array specifies the database connection or
 * connections that DSF may use.  DSF is able to connect
 * to multiple databases.
 *
 * Each database connection is specified as an array of settings,
 * similar to the following:
 * @code
 * array(
 *   'driver'    => 'mysql',
 *   'database'  => 'databasename',
 *   'username'  => 'username',
 *   'password'  => 'password',
 *   'host'      => 'localhost',
 *   'port'      => '3306',
 *   'collation' => 'utf8_general_ci'
 * );
 * @endcode
 *
 * The "driver" property indicates what DSF database driver the
 * connection should use.  This is usually the same as the name of the
 * database type, such as mysql or sqlite, but not always.  The other
 * properties will vary depending on the driver.  For SQLite, you must
 * specify a database file name in a directory that is writable by the
 * webserver.  For most other drivers, you must specify a
 * username, password, host, and database name.
 *
 * Some database engines support transactions.  In order to enable
 * transaction support for a given database, set the 'transactions' key
 * to TRUE.  To disable it, set it to FALSE.  Note that the default value
 * varies by driver.  For MySQL, the default is FALSE since MyISAM tables
 * do not support transactions.
 *
 * For a single database configuration, the following is sufficient:
 * @code
 * $databases['default']['default'] = array(
 *   'driver'    => 'mysql',
 *   'database'  => 'databasename',
 *   'username'  => 'username',
 *   'password'  => 'password',
 *   'host'      => 'localhost',
 *   'port'      => '',
 *   'collation' => 'utf8_general_ci'
 * );
 * @endcode
 */

$databases = array (
    'driver'    => 'mysql',
    'database'  => 'dsf',
    'username'  => 'root',
    'password'  => '1029384756',
    'host'      => 'localhost',
    'port'      => '',
    'collation' => ''
);

/**
 * Is database configured.
 *
 * This parameter will be changed the first time thereis an
 * access to the DSF, and don't need to be changed manually.
 */

$is_database_configured = false;

/**
 * Base URL.
 *
 * The base_url property is the main DSF url, it will be used as link to the
 * logos for the DSF front page.
 *
 * You might also want to force users to use a given domain.
 * See the .htaccess file for more information.
 *
 * Examples:
 *   $base_url = 'http://www.example.com';
 *   $base_url = 'http://www.example.com:8888';
 *   $base_url = 'http://www.example.com/dsf';
 *   $base_url = 'https://www.example.com:8888/dsf';
 *
 * It is not allowed to have a trailing slash; DSF will add it
 * for you.
 */

$base_url = 'http://www.example.com';

/**
 * Site Name:
 *
 * Your DSF site name.
 *
 * Examples:
 *   $site_name = 'dsf';
 *   $site_name = 'Damn Small Forums';
 *   $site_name = 'My Forum';
 */

$site_name = 'Damn Small Forums';

/**
 * Site Slogan:
 *
 * Your DSF site slogan.
 *
 * Examples:
 *   $site_slogan = 'Smallest forum ever';
 *   $site_slogan = '| A forum could never be so <del>crappy</del> small';
 *   $site_slogan = 'Small as your ****';
 */

$site_slogan = 'A forum could never be so <del>crappy</del> small';

/**
 * Theme:
 *
 * The theme used for the pages.
 * Themes must be placed on the themes folder.
 *
 * Examples:
 *   $theme = 'dsf';
 *   $theme = 'my_template';
 *   $theme = 'coll_colors';
 */

$theme = 'dsf';

/**
 * PHP settings:
 *
 * To see what PHP settings are possible, including whether they can be set at
 * runtime (by using ini_set()), read the PHP documentation:
 * http://www.php.net/manual/en/ini.list.php
 * See drupal_initialize_variables() in includes/bootstrap.inc for required
 * runtime settings and the .htaccess file for non-runtime settings. Settings
 * defined there should not be duplicated here so as to avoid conflict issues.
 */

/**
 * Some distributions of Linux (most notably Debian) ship their PHP
 * installations with garbage collection (gc) disabled. Since Drupal depends on
 * PHP's garbage collection for clearing sessions, ensure that garbage
 * collection occurs by using the most common settings.
 */
ini_set('session.gc_probability', 1);
ini_set('session.gc_divisor', 100);

/**
 * Set session lifetime (in seconds), i.e. the time from the user's last visit
 * to the active session may be deleted by the session garbage collector. When
 * a session is deleted, authenticated users are logged out, and the contents
 * of the user's $_SESSION variable is discarded.
 */
ini_set('session.gc_maxlifetime', 200000);

/**
 * Set session cookie lifetime (in seconds), i.e. the time from the session is
 * created to the cookie expires, i.e. when the browser is expected to discard
 * the cookie. The value 0 means "until the browser is closed".
 */
ini_set('session.cookie_lifetime', 2000000);

/**
 * If you encounter a situation where users post a large amount of text, and
 * the result is stripped out upon viewing but can still be edited, Drupal's
 * output filter may not have sufficient memory to process it.  If you
 * experience this issue, you may wish to uncomment the following two lines
 * and increase the limits of these variables.  For more information, see
 * http://php.net/manual/en/pcre.configuration.php.
 */
# ini_set('pcre.backtrack_limit', 200000);
# ini_set('pcre.recursion_limit', 200000);

/**
 * Drupal automatically generates a unique session cookie name for each site
 * based on on its full domain name. If you have multiple domains pointing at
 * the same Drupal site, you can either redirect them all to a single domain
 * (see comment in .htaccess), or uncomment the line below and specify their
 * shared base domain. Doing so assures that users remain logged in as they
 * cross between your various domains.
 */
# $cookie_domain = 'example.com';